IRIX 6.2 Development Libraries

home *** CD-ROM | disk | FTP | other *** search

/ IRIX 6.2 Development Libraries / SGI IRIX 6.2 Development Libraries.iso / relnotes / ViewKit_dev / ch3.z / ch3

Wrap

Text File | 1997-09-04 | 30.5 KB | 859 lines

- 1 - 3. _O_v_e_r_v_i_e_w +o n32 and 64-bit libraries are now provided. +o Debug library naming has been changed to make the debug libraries much easier to use. To use a debugging version of the ViewKit libraries, install the ViewKit_dev.sw.debug, and then simply set the LLLLDDDD____LLLLIIIIBBBBRRRRAAAARRRRYYYY____PPPPAAAATTTTHHHH environment variable to /usr/lib/debug before running your program. The debugging library has full symbols, so stack traces will be more informative. The debugging viewkit library also prints various warnings, and makes liberal use of assertions to catch misuse of the the library. +o To allow for future versioning, libXpm.so has been renamed to libXpm.so.1, and libXpm.so is now a symbolic link to libXpm.so.1. +o libXpm is now version 3.4f (previously it was version 3.2g). 3.1 _V_i_e_w_K_i_t__B_u_g__F_i_x_e_s This chapter lists the major bugs fixed in ViewKit since the IRIX 5.3 release. +o Corrected a number of references to the default colormap to use the correct colormap. +o We have made a systematic effort, using _p_u_r_i_f_y, to find and fix memory leaks. All known ViewKit-induced memory leaks and malloc problems have been fixed. +o _V_k_F_i_l_e_S_e_l_e_c_t_i_o_n_D_i_a_l_o_g can now set a filter on multiple dialogs. +o _V_k_C_o_m_p_o_n_e_n_t::_a_f_t_e_r_R_e_a_l_i_z_e_H_o_o_k now gets called for dialogs. +o The file selection dialog now sets its directory correctly, even if there is more than one file selection dialog up at a time. +o Several manual page errors and omissions have been fixed. +o Several classes that did not have missing manual pages now have them. - 2 - +o Several schemes problems have been corrected. +o _V_k_C_o_m_p_o_n_e_n_t now calls afterRealizeHook(), even if the parent is already realized when show() is called. +o _V_k_D_o_u_b_l_e_B_u_f_f_e_r now draws the initial display correctly, even if it was not realized when it was drawn. +o _V_k_F_o_r_k_I_O::_c_l_e_a_r_H_i_s_t_o_r_y no longer goes into an infinite loop. +o _V_k_G_r_a_p_h now returns the correct node after a node is removed. +o _V_k_G_r_a_p_h now passes back the X event where appropriate and it has an event. +o Menu items are now in right place when addAction called after menu built. +o Initial menu pane hide now works. +o Option menu getIndex() now returns 0 initially, not -1. +o _V_k_N_L_S no longer puts up an empty dialog if no resource string is set. +o Fixed the core dump in _V_k_T_a_b_P_a_n_e_l when adding or deleting tabs. +o _V_k_T_a_b_P_a_n_e_l's popup menu can no longer be torn off -- doing so was a problem. +o Fixed the core dump when _V_k_T_a_b_P_a_n_e_l was deleted while a work proc was pending. +o Set the background of the _V_k_T_a_b_P_a_n_e_l drawing area to eliminate color flashing. +o xpm.h is now installed in /usr/include/X11, where most applications expect it. To maintain compatibility with IRIX 5.3 and earlier, there is with a symlink from /usr/include/Vk. +o Xpm has been upgraded to xpm version 3.4. This fixes some core dumps. +o _V_k_C_r_e_a_t_e_X_P_M_P_i_x_m_a_p now handles non-default Visuals correctly. - 3 - +o Changed demo file installation to be owner=root, group=sys, modes 755(directories) and 644(files. This change was in deference to those who felt that looser permissions presented a security problem. 3.2 _n_3_2__a_n_d__6_4_-_b_i_t__l_i_b_r_a_r_i_e_s n32 versions of all ViewKit libraries are provided in /usr/lib32. 64-bit versions of all ViewKit libraries are provided in /usr/lib64. For instructions on building the ViewKit demo programs in either n32 or 64-bits, see the top-level README and Makefile. 3.3 _D_e_b_u_g__l_i_b_r_a_r_i_e_s__h_a_v_e__b_e_e_n__r_e_n_a_m_e_d__f_o_r__e_a_s_i_e_r__u_s_e There are no more ViewKit *_d.a debug libraries, requiring relinking your application to use them. Debug libraries are now DSO's that are installed in the debug subdirectory below the corresponding normal DSO. The library names are identical. This means that an application can link normally, rather than with a special debug library. By setting the environment variable LLLLDDDD____LLLLIIIIBBBBRRRRAAAARRRRYYYY____PPPPAAAATTTTHHHH, the application can run with the debug library. For example, to run with the 64-bit debug libraries, just: +o Link normally, such as with "-L/usr/lib64 -lvk". +o When you want to run with the debug libraries, set the environment variable LLLLDDDD____LLLLIIIIBBBBRRRRAAAARRRRYYYY____PPPPAAAATTTTHHHH to /usr/lib64/debug. As always, the debug libraries have a number of aaaasssssssseeeerrrrtttt statements. These are intended to check both the application's use of the library and internal library consistency. The assertions are not as complete as we would like, but we are adding more over time. - 4 - 3.4 _C_l_a_s_s__E_n_h_a_n_c_e_m_e_n_t_s We have been very careful to maintain binary compatibility when enhancing a class. Some changes introduce entirely new, non-conflicting, behavior for the class. Other changes introduce a choice between a new behavior and the way the class has behaved in the past. In such a case, to preserve compatibility, the default remains to run the old way. An application has to do something, such as set a resource, to get the new behavior. 3.4.1 _V_k_A_p_p__E_n_h_a_n_c_e_m_e_n_t_s For more information about any of these enhancements, see _m_a_n _V_k_A_p_p(_3_X). 3.4.1.1 _V_k_A_p_p_:_:_r_u_n_(_) _V_k_A_p_p::_r_u_n has increased flexibility. It now allows the application more control over how the X event loop is handled. 3.4.1.2 _V_k_A_p_p_:_:_u_s_e_S_c_h_e_m_e_s_(_) The static function _V_k_A_p_p::_u_s_e_S_c_h_e_m_e_s(_c_h_a_r *_v_a_l) has been added to let schemes be turned on or off programmatically. Schemes defaults to being on. For example, +o uuuusssseeeeSSSScccchhhheeeemmmmeeeessss((((""""aaaallllllll"""")))) will turn schemes on +o uuuusssseeeeSSSScccchhhheeeemmmmeeeessss((((""""nnnnoooonnnneeee"""")))) will turn schemes off 3.4.1.3 _N_e_w__r_e_s_o_u_r_c_e_:__q_u_i_t_M_o_d_e _q_u_i_t_M_o_d_e is a new string- valued resource (default value: eeeeaaaacccchhhh). _V_k_A_p_p::_q_u_i_t_Y_o_u_r_s_e_l_f() calls _o_k_T_o_Q_u_i_t for each window. In the past (and still true by default) if any of them returns success, then the application quits. If, however, _q_u_i_t_M_o_d_e is set to aaaallllllll then the application quits if, and only if, all windows agree to. _N_O_T_E: _t_h_i_s _d_o_e_s _n_o_t _a_p_p_l_y _w_h_e_n _t_h_e _w_i_n_d_o_w _m_a_n_a_g_e_r _t_r_i_e_s _t_o _c_l_o_s_e _a _w_i_n_d_o_w. _T_o _c_o_n_t_r_o_l _t_h_a_t _b_e_h_a_v_i_o_r, _a_n _a_p_p_l_i_c_a_t_i_o_n _m_u_s_t _o_v_e_r_r_i_d_e VkSimpleWindow::handleWmDeleteMessage() _a_n_d/_o_r VkSimpleWindow::handleWmQuitMessage(). _F_r_o_m _t_h_e_r_e, _t_h_e _a_p_p_l_i_c_a_t_i_o_n _c_a_n _c_a_l_l VkApp::quitYourself() _i_f _i_t _w_a_n_t_s _t_o. - 5 - 3.4.1.4 _V_k_A_p_p_:_:_s_e_t_F_a_l_l_b_a_c_k_s_(_) _s_t_a_t_i_c _v_o_i_d _V_k_A_p_p::_s_e_t_F_a_l_l_b_a_c_k_s(_c_h_a_r **_f_a_l_l_b_a_c_k_s) sets _f_a_l_l_b_a_c_k_s as the _s_p_e_c_i_f_i_c_a_t_i_o_n__l_i_s_t needed to call _X_t_A_p_p_S_e_t_F_a_l_l_b_a_c_k_R_e_s_o_u_r_c_e_s(_3_X). 3.4.2 _V_k_C_o_m_p_o_n_e_n_t__E_n_h_a_n_c_e_m_e_n_t_s For more information about any of these enhancements, see _m_a_n _V_k_C_o_m_p_o_n_e_n_t(_3_X). 3.4.2.1 _V_k_C_o_m_p_o_n_e_n_t_:_:_l_o_a_d_O_b_j_e_c_t_(_) _s_t_a_t_i_c _V_k_C_o_m_p_o_n_e_n_t *_l_o_a_d_O_b_j_e_c_t(_c_o_n_s_t _c_h_a_r *_n_a_m_e, _W_i_d_g_e_t _p_a_r_e_n_t, _c_o_n_s_t _c_h_a_r *_c_l_a_s_s_N_a_m_e, _c_o_n_s_t _c_h_a_r *_f_i_l_e_n_a_m_e) supports dynamic loading of objects, as supported by RapidApp. Objects must be set up properly for this to work. See _m_a_n _V_k_C_o_m_p_o_n_e_n_t and _m_a_n _V_k_C_a_l_l_b_a_c_k_O_b_j_e_c_t or the RapidApp documentation for details. 3.4.2.2 _V_k_C_o_m_p_o_n_e_n_t_:_:_s_e_t_D_e_f_a_u_l_t_R_e_s_o_u_r_c_e_s_(_) _v_o_i_d _V_k_C_o_m_p_o_n_e_n_t::_s_e_t_D_e_f_a_u_l_t_R_e_s_o_u_r_c_e_s ( _c_o_n_s_t _W_i_d_g_e_t _w, _c_o_n_s_t _S_t_r_i_n_g *) now supports a syntax (a prepended "+" or "-") that qualifies resources for such things as overriding SGI Schemes. 3.4.3 _V_k_D_i_a_l_o_g_M_a_n_a_g_e_r_:_:_p_r_e_p_o_s_t_C_a_l_l_b_a_c_k This callback is invoked just before a dialog is displayed. For more information see _m_a_n _V_k_D_i_a_l_o_g_M_a_n_a_g_e_r(_3_X). 3.4.4 _V_k_M_e_n_u__E_n_h_a_n_c_e_m_e_n_t_s For more information about any of these enhancements, see _m_a_n _V_k_M_e_n_u(_3_X). 3.4.4.1 _V_k_M_e_n_u_:_:_s_e_t_M_e_n_u_B_a_r__(_) _V_k_M_e_n_u::_s_e_t_M_e_n_u_B_a_r (_V_k_M_e_n_u_D_e_s_c *_m_e_n_u_D_e_s_c, _X_t_P_o_i_n_t_e_r _c_l_i_e_n_t_D_a_t_a) is an overloaded entry to allow controlling default client data. This effectively allows passing zero as client data (by setting the default client data to zero). There remains no way to tell passing an explicit zero from just not initializing the client data in the _V_k_M_e_n_u_D_e_s_c structure. 3.4.4.2 _V_k_M_e_n_u_:_:_g_e_t_L_a_b_e_l__(_) _V_k_M_e_n_u_I_t_e_m::_g_e_t_L_a_b_e_l(_v_o_i_d) was added for symmetry with the existing _V_k_M_e_n_u_I_t_e_m::_s_e_t_L_a_b_e_l(). 3.4.4.3 _V_k_M_e_n_u__s_e_p_a_r_a_t_o_r_s__c_a_n__n_o_w__h_a_v_e__n_a_m_e_s Menu separators can now have names. This is so that they can be manipulated just like any other menu item. - 6 - 3.4.4.4 _P_u_l_l_d_o_w_n _m_e_n_u_s _m_a_y _n_o_w _b_e _p_l_a_c_e_d _i_n _t_h_e _o_v_e_r_l_a_y _p_l_a_n_e_s. This addition allows putting ViewKit pulldown menus in the overlay planes. Doing so prevents expose events from disturbing such things as complex GL rendering. The current implementation is global. For a single application, either all menus go in the popu planes or none of them do. That may be relaxed in a future release. 3.4.4.4.1 _H_o_w__T_o__E_n_a_b_l_e__P_u_l_l_d_o_w_n__M_e_n_u_s__I_n__T_h_e__P_o_p_u_p__P_l_a_n_e_s By default, pulldown menus appear in the normal planes. There are three ways to enable pulldowns in the popup planes: +o Call _V_k_M_e_n_u::_u_s_e_O_v_e_r_l_a_y_M_e_n_u_s(_T_R_U_E) in your application. This will force pulldowns in the popup planes, with no way to put them back in the normal planes without recompiling. +o Put the resource string "*useOverlayMenus: True" in your application's app-defaults file. This will put pulldowns in the popup planes by default, but allow users to use the normal planes by changing their .Xdefaults file. +o Ask the user to add the "-useOverlayMenus" command line switch when they run the application. This will put pulldowns in the normal planes by default, but allow the user to explicitly ask that the popup planes be used. 3.4.4.4.2 _D_i_s_a_d_v_a_n_t_a_g_e_s _O_f _P_u_l_l_d_o_w_n _M_e_n_u_s _I_n _T_h_e _P_o_p_u_p _P_l_a_n_e_s Why not put pulldown menus in the popup planes all of the time? There are several disadvantages to using the popup planes, so menus should be put there only when the advantages outweigh the disadvantages: +o The colormap in the popup planes only has three color entries. (The fourth entry is a transparent pixel.) Because there are fewer colors available, menus in the popup planes have a different appearance. If you have items in your menu pulldowns other than labels (e.g. cascade buttons or toggle buttons), they may not look correct in some of the less-common color schemes. +o Other applications that are using the popup planes at the same time will display in the wrong colors when a pulldown menu appears (i.e. colors will flash). This happens because the pulldown menu colormap will get installed and replace any previous overlay colormap. - 7 - +o When a pulldown menu in the popup plane is torn off, 4Dwm puts the tear-off in the popup planes. The title bar of the window appears with the wrong colors, and as with (2), the window appears with the wrong colors when another application uses the popup planes (e.g. 4Dwm's root-window popup menu). 3.4.4.4.3 _D_e_m_o _P_r_o_g_r_a_m _F_o_r _P_u_l_l_d_o_w_n _M_e_n_u_s _I_n _T_h_e _P_o_p_u_p _P_l_a_n_e_s Running the example program "vkmenu" shows that the expose counter increments each time a menubar item is selected and dismissed. Running "vkmenu -useOverlayMenus" shows that the expose counter does not change when pulldown menus appear and disappear, since no expose events are generated. +o For more information about the demo program, see /_u_s_r/_s_h_a_r_e/_s_r_c/_V_i_e_w_K_i_t/_M_e_n_u_s/_R_E_A_D_M_E. +o For more information about the affected ViewKit classes, see _m_a_n _V_k_A_p_p(_3_X), _m_a_n _V_k_M_e_n_u(_3_X), _m_a_n _V_k_S_u_b_M_e_n_u(_3_X). 3.4.5 _V_k_M_e_n_u_B_a_r_:_:_s_h_o_w_H_e_l_p_P_a_n_e_(_) _V_k_M_e_n_u_B_a_r::_s_h_o_w_H_e_l_p_P_a_n_e(_B_o_o_l_e_a_n _s_h_o_w = _T_R_U_E) controls whether the Help pane is visible or not. For more information see _m_a_n _V_k_M_e_n_u_B_a_r(_3_X). 3.4.6 _V_k_N_a_m_e_L_i_s_t__E_n_h_a_n_c_e_m_e_n_t_s For more information about any of these enhancements, see _m_a_n _V_k_N_a_m_e_L_i_s_t(_3_X). 3.4.6.1 _V_k_N_a_m_e_L_i_s_t__h_a_s__n_e_w__m_e_m_b_e_r__f_u_n_c_t_i_o_n_s Some new utility functions have been added. +o _V_k_N_a_m_e_L_i_s_t::_g_e_t_I_n_d_e_x(); +o _V_k_N_a_m_e_L_i_s_t::_r_e_m_o_v_e(_c_h_a_r *); +o _V_k_N_a_m_e_L_i_s_t::_r_e_m_o_v_e(_i_n_t _i_n_d_e_x, _i_n_t _c_o_u_n_t=_1); 3.4.6.2 _P_r_o_b_l_e_m__w_i_t_h__V_k_N_a_m_e_L_i_s_t__o_p_e_r_a_t_o_r_s Some of the _V_k_N_a_m_e_L_i_s_t operators are a problem, because they allocate memory that must later be freed by the caller. Because operators are often used in expressions, this is an open invitation to memory leaks. Several corresponding new conventional functions have been added. They each make it - 8 - more obvious that there might be something to be freed. One of them (_g_e_t_S_u_b_s_t_r_i_n_g_s()) is also considerably more efficient. Applications are strongly encouraged to switch to the new conventional functions. +o _V_k_N_a_m_e_L_i_s_t::_g_e_t_S_t_r_i_n_g(); +o _V_k_N_a_m_e_L_i_s_t::_g_e_t_S_u_b_s_t_r_i_n_g_s(); +o _V_k_N_a_m_e_L_i_s_t::_g_e_t_S_t_r_i_n_g_T_a_b_l_e(); +o _V_k_N_a_m_e_L_i_s_t::_g_e_t_X_m_S_t_r_i_n_g_T_a_b_l_e() +o _V_k_N_a_m_e_L_i_s_t::_f_r_e_e_X_m_S_t_r_i_n_g_T_a_b_l_e() 3.4.7 _V_k_R_u_n_O_n_c_e_2__n_o_t_e For more information about _V_k_R_u_n_O_n_c_e or _V_k_R_u_n_O_n_c_e_2, see _m_a_n _V_k_R_u_n_O_n_c_e(_3_X) and _m_a_n _V_k_R_u_n_O_n_c_e_2(_3_X). _V_k_R_u_n_O_n_c_e_2 is very similar to _V_k_R_u_n_O_n_c_e, but there are subtle differences between these two classes. _V_k_R_u_n_O_n_c_e_2 adds several new member functions. It also does error checking that _V_k_R_u_n_O_n_c_e does not. We suggest that all applications that can do so use _V_k_R_u_n_O_n_c_e_2, rather than _V_k_R_u_n_O_n_c_e. 3.4.8 _V_k_S_i_m_p_l_e_W_i_n_d_o_w__E_n_h_a_n_c_e_m_e_n_t_s For more information about any of these enhancements, see _m_a_n _V_k_S_i_m_p_l_e_W_i_n_d_o_w(_3_X). 3.4.8.1 _V_k_S_i_m_p_l_e_W_i_n_d_o_w__p_r_o_v_i_d_e_s__a_c_c_e_s_s__t_o__Q_u_i_c_k_H_e_l_p QuickHelp provides a status line at the bottom of the window and/or popup balloon help. The feature is controlled by X resources, so all that is needed to enable it for any particular application is the right settings in the application's X default resources file. Note: There is also an experimental programmatic interface to QuickHelp. _T_h_i_s _i_n_t_e_r_f_a_c_e _i_s _s_u_b_j_e_c_t _t_o _c_h_a_n_g_e _i_n _a _f_u_t_u_r_e _r_e_l_e_a_s_e. 3.4.8.2 _V_k_S_i_m_p_l_e_W_i_n_d_o_w_:_:_g_e_t_W_i_n_d_o_w_(_) _s_t_a_t_i_c _V_k_S_i_m_p_l_e_W_i_n_d_o_w *_g_e_t_W_i_n_d_o_w(_V_k_C_o_m_p_o_n_e_n_t *_c_o_m_p_o_n_e_n_t) returns the _V_k_S_i_m_p_l_e_W_i_n_d_o_w object (or subclass) that contains the given _V_k_C_o_m_p_o_n_e_n_t. - 9 - 3.4.9 _V_k_T_a_b_P_a_n_e_l__I_m_p_r_o_v_e_d__A_p_p_e_a_r_a_n_c_e _V_k_T_a_b_P_a_n_e_l previously had a flat appearance for its tabs, rather than providing tabs with a shaded 3D appearance. This was considered more of a bug to be fixed than a feature. _V_k_T_a_b_P_a_n_e_l tab drawing has now been improved so that the tabs have an (optional) 3D appearance. The new 3D appearance is controlled by a new _V_k_T_a_b_P_a_n_e_l resource, _u_s_e_3_D_T_a_b_s (default TRUE). If the resource is set to TRUE, the tabs are drawn with a shaded 3D appearance. _V_k_T_a_b_P_a_n_e_l also has two new member functions so that applications can cooperate with the improved (fixed) appearance. Applications that construct pixmaps for tab labels should set _u_s_e_3_D_T_a_b_s = _T_R_U_E and use the new functions to get their backgrounds. +o Pixel getSelectedTabBG() +o Pixel getUnselectedTabBG() The member function GC gc() is now deprecated, in favor of the new functions, because it is meaningful only with _u_s_e_3_D_T_a_b_s = _F_A_L_S_E. Apps that construct pixmaps for tab labels should set _u_s_e_3_D_T_a_b_s = _T_R_U_E and use the new functions to get their backgrounds. For more information see _m_a_n _V_k_T_a_b_P_a_n_e_l(_3_X). 3.4.10 _V_k_W_i_n_d_o_w__E_n_h_a_n_c_e_m_e_n_t_s For more information about any of these enhancements, see _m_a_n _V_k_W_i_n_d_o_w(_3_X). 3.4.10.1 _V_k_W_i_n_d_o_w_:_:_g_e_t_W_i_n_d_o_w_(_) _s_t_a_t_i_c _V_k_W_i_n_d_o_w *_g_e_t_W_i_n_d_o_w(_V_k_C_o_m_p_o_n_e_n_t *_c_o_m_p_o_n_e_n_t) returns the _V_k_W_i_n_d_o_w object (or subclass) that contains the given _V_k_C_o_m_p_o_n_e_n_t. 3.4.10.2 _V_k_W_i_n_d_o_w_:_:_g_e_t_M_e_n_u_(_) _s_t_a_t_i_c _V_k_M_e_n_u_B_a_r *_g_e_t_M_e_n_u(_V_k_C_o_m_p_o_n_e_n_t *_c_o_m_p_o_n_e_n_t) returns the menubar used by the window that contains the given _V_k_C_o_m_p_o_n_e_n_t. 3.5 _N_e_w__C_l_a_s_s_e_s The following classes are new since IRIX 5.3. - 10 - 3.5.1 _V_k_C_o_l_o_r_C_h_o_o_s_e_r_D_i_a_l_o_g For more information, see _m_a_n _V_k_C_o_l_o_r_C_h_o_o_s_e_r_D_i_a_l_o_g(_3_X). 3.5.2 _V_k_C_u_t_P_a_s_t_e The _V_k_C_u_t_P_a_s_t_e class provides programmers with a simple and clean API for implementing cut and paste and drag and drop functionality in their application. For more information, see _m_a_n _V_k_C_u_t_P_a_s_t_e(_3_X). 3.5.3 _V_k_M_o_v_i_e_B_u_t_t_o_n _V_k_M_o_v_i_e_B_u_t_t_o_n is a multimedia button component that plays a movie within a pushable button. This class is most effective with a short movie that acts as an animation. For more information, see _m_a_n _V_k_M_o_v_i_e_B_u_t_t_o_n(_3_X). 3.5.4 _V_k_M_o_v_i_e_P_l_a_y_e_r _V_k_M_o_v_i_e_P_l_a_y_e_r is a multimedia component that plays a movie and supports simple operations such as playing, stoping, rewinding. For more information, see _m_a_n _V_k_M_o_v_i_e_P_l_a_y_e_r(_3_X). 3.5.5 _V_k_P_r_o_g_r_e_s_s_D_i_a_l_o_g This is a new SGI Style Guide- compliant class for displaying the approximate amount of a task that has been completed. For more information, see _m_a_n _V_k_P_r_o_g_r_e_s_s_D_i_a_l_o_g(_3_X). 3.5.6 _V_k_S_o_A_p_p _V_k_S_o_A_p_p is a class used by all Inventor ViewKit applications to handle initialization. For more information, see _m_a_n _V_k_S_o_A_p_p(_3_X). 3.5.7 _V_k_T_a_b_b_e_d_D_e_c_k _V_k_T_a_b_b_e_d_D_e_s_k combines a _V_k_T_a_b_P_a_n_e_l and a _V_k_D_e_c_k, to give an appearance somewhat like a set of tabbed cards. For more information, see _m_a_n _V_k_T_a_b_b_e_d_D_e_c_k(_3_X). - 11 - 3.6 _N_e_w__G_l_o_b_a_l__F_u_n_c_t_i_o_n_s The following global functions are new since IRIX 5.3. 3.6.1 _V_k_S_e_t_H_i_g_h_l_i_g_h_t_i_n_g_P_i_x_m_a_p For more information, see _m_a_n _V_k_S_e_t_H_i_g_h_l_i_g_h_t_i_n_g_P_i_x_m_a_p(_3_X). 3.6.2 _V_k_C_o_n_f_i_g_u_r_e_W_i_n_d_o_w For more information, see _m_a_n _V_k_C_o_n_f_i_g_u_r_e_W_i_n_d_o_w(_3_X). 3.7 _N_e_w__l_i_b_r_a_r_y_:__l_i_b_v_k_S_G_I libvk is a portable library. There are versions available for most Unix workstations. libvkSGI has been created for classes that philosophically belong in libvk, but which are SGI-specific. In this release, libvkSGI includes: 3.8 _N_e_w__l_i_b_r_a_r_y_:__l_i_b_V_k_E_Z_._a 3.9 _l_i_b_X_p_m__u_p_g_r_a_d_e_s 3.9.1 _X_p_m__d_o_c_u_m_e_n_t_a_t_i_o_n We now pass through the documentation files that we get with Xpm. These files are shipped as the subsystem _V_i_e_w_K_i_t__d_e_v._m_a_n._x_p_m-_d_o_c, and are installed in /usr/share/doc/Xpm. The new on-line _X_p_m(_3_x) man page also tells where to find these documents. 3.9.2 _l_i_b_X_p_m_._s_o__h_a_s__b_e_c_o_m_e__l_i_b_X_p_m_._s_o_._1 To provide for future incompatible libXpm DSO's, libXpm.so is now called libXpm.so.1. There is a symbolic link, libXpm.so, that points to libXpm.so.1. This should cause no problems for any existing application. 3.9.3 _l_i_b_X_p_m__i_s__n_o_w__v_e_r_s_i_o_n__3_._4 The IRIX 5.3 release contained Xpm version 3.2g. SGI never released Xpm version 3.3, which was incompatible with 3.2. The current release is Xpm 3.4, which is both source and binary compatible with Xpm version 3.2. - 12 - 3.9.4 _X_p_m__E_n_h_a_n_c_e_m_e_n_t_s__S_i_n_c_e__I_R_I_X__5_._3__(_X_p_m__3_._2_g_) +o The colorTable member of the XpmAttributes structure is now an (XpmColor*) in order to be compatible with an XpmImage colorTable. However in order to be backward compatible this field is cast to (XpmColor **), which is equivalent to (char ***), when it is used with the old flags XpmInfos and XpmReturnInfos. To handle the new type, the new flags XpmColorTable and XpmReturnColorTable have been defined. NOTE: code that directly accesses the XpmAttributes.colorTable, such as "... = XpmAttributes.colorTable[i][1]" will need to be changed to something like "... = XpmAttributes.colorTable[i].symbolic" +o The XpmInfo struct has been extended to avoid having to deal with an XpmAttributes at the lower level. The idea is that all the data stored in an Xpm file can be retrieved through both an XpmImage and an XpmInfo struct. +o XpmUndefPixel is defined and exported by xpm.h in order to let clients providing their own colorTable when writing out an Xpm file. +o A new function and a new define should help client figuring out with which Xpm library version they are working. These are XpmIncludeVersion and XpmLibraryVersion(). +o XPM1 files are supported. +o A new function is provided to get an error string related to the returned error code. +o The parser is more flexible about the way strings are distributed on lines. A single line XPM file can be read. +o A new level interface is provided to allow applications to do either icon editing or data caching. +o New structures are provided to deal with the lower level: XpmImage, XpmColor, XpmInfos. +o xpm.h defines XpmFormat, XpmVersion, and XpmRevision numbers. - 13 - 3.9.5 _X_p_m__B_u_g__F_i_x_e_s__S_i_n_c_e__I_R_I_X__5_._3 +o A segmentation fault occurring in some weird case. +o The list of pixels returned in XpmAttributes was wrong when two colors were defined as None in the read XPM. +o The parser was skipping white space reading extension strings. This has been fixed so extension lines are now returned exactly as they are. +o When writing an XPM file, '-' characters are replaced with '_' characters in the array name, in order to get a valid C syntax name. +o XYPixmap format images are now handled correctly. +o XPM1 file with names using multiple '_' characters are now handled correctly. +o Reading certain binary files was leading to a bus error. +o The ? character is no longer used when writing an XPM file in order to avoid possible ANSI trigraphs.